Release 10.1A: OpenEdge Data Management:
Database Administration

Database

Displays general database status information. Figure 19–10 shows a sample Database Status display.

09/15/03            Status: database 11:01:01 Database was started at:          09/15/03 9:17 It has been up for:               1:43:37 Database state:                   Open (1) Database damaged flags:           None Integrity flags:                  None Most recent database open:        09/15/03 9:17 Previous database open:           09/15/03 9:17 Local cache file time stamp:      09/10/03 21:41 Database block size:              4029 bytes Number of blocks allocated:       324 (1268 kb) Empty blocks:                     20 (6%) Free blocks:                      0 (0%) RM Blocks with Free Space:        4 (1%) Last transaction id:              172 Highest table number defined:     9 Database version number:          143 Shared memory version number:     10003

Figure 19–10: PROMON Database Status display

The display in Figure 19–10 contains the following fields:

Database state — The current operating mode of the database. Table 19–7 describes the possible states.

Table 19–7: Database states 

State	Description
Open.	The database is open.
Not modified since last open.	The database is closed.
Recovery.	The database is performing crash recovery.
Index repair.	The PROUTIL IDXBUILD utility is running to rebuild indexes.
Restore.	The database is being restored.

Database damaged flags — The state of the database. Table 19–8 lists the possible flags.

Table 19–8: Database damaged flags 

State	Description
None	Normal.
Opened with -F	Crash recovery skipped. The database might be damaged.
Crashed with -i	Crashed without integrity. The database is damaged.
Crashed with -r	Crashed with buffered I/O. The database might be damaged.

Integrity flags — The integrity mode in which the database is running. Table 19–9 lists the possible flags.

Table 19–9: Integrity flags 

State	Description
None	Normal.
Executing with -i	A crash in this state will damage the database.
Executing with -r	A crash in this state might damage the database.

Most recent database open — The date and time when the broker for this database was started.
Previous database open — The date and time when the database was previously started.
Local cache file time stamp — The time stamp used to check the validity of the schema cache file. For more information, see the description of the Schema Cache File (-cache) parameter in Chapter 18, " Database Startup Parameters."
Database block size — The database block size in bytes.
Number of blocks allocated — The total number of blocks allocated to the database.
RM Blocks with free space — The total number of blocks in the RM chain.
Highest table number defined — The number of tables defined in the database.
Database version number — Identifies the structures of all database-related data that is resident on disk. This number is used to match different executable versions with the correct database structures.
Shared memory version number — Identifies the version of all data structures that are resident in shared memory and used by the database manager. This number is used to ensure that all executables accessing shared memory agree on what data is kept in shared memory and how that data is accessed. The shared-memory version number changes more frequently than the database version number.